Please note: This article applies to 

DocumentsCorePack ServerBased Document Generation & Processing
for Microsoft CRM 2013, 2015 and Microsoft CRM 2015/2016

ON PREMISE AND IFD ONLY 

(Click here for information on debugging in DocumentsCorePack Online) 

+++++++++++++++++++++++++++++++++++++++++++++++++++

This article describes two different possibilities to activate debugging for DocumentsCorePack:

Solution 1: How to enable debugging using the AutoMerge Configuration 

 Figure 1: Microsoft Dynamics CRM 2015 and lower

Example for Microsoft Dynamics CRM 2015/2016 and higher:

Figure 2: Microsoft Dynamics CRM 2015/2016 and higher

Figure 3: All solutions > AutoMerge Core Solution

Figure 4: AutoMerge Config

Solution 2: How to enable debugging manually via mscrm-addons.com Settingskeys      

Figure 6: Active MSCRM-ADDONS.com Products

This action will open the AutoMerge SettingsKey. Look for debugging and double-click on it.

Figure 7: AutoMerge debug 

Step 4

This action will open the debug SettingsKey. Set the KeyValue on true (highlighted in yellow)
and click on the icon in the right corner at the bottom of the window (highlighted as well in yellow) in order to save your settings.

Figure 8: debug SettingsKey

Step 5

You will also have to activate the file-debugging. Therefore, click on filedebugging in the 
AutoMerge Settingskey and apply Step 4 also to filedebugging. 

Figure 9: filedebugging SettingsKey


Debug and filedebugging are now active. The log-files will be saved in the log-folder in your AutoMerge installation folder.

Please send the files in the log-folder with an error description to our support address (support@mscrm-addons.com).

How to access the logfiles     

Navigate to the installation-path of AutoMerge and send the files in the log-folder with an error description to our support address (support@mscrm-addons.com).

Example how the path could look like:

C:\Program Files (x86)\PTM EDV-Systeme GmbH\AutoMerge for Microsoft CRM 2013\log

Figure 10: Example path I

Figure 11: Example path II

Figure 12: Example path III

Figure 13: Example path IV

 

How to activate local DCP service debugging

Please note: If you have a DocumentsCorePack service issue, please activate Debugging this way:

Go to the start-pane and look for the DocumentsCorePack ServiceManagement. 
In the so opened window, you have the possibility to activate debugging, like you can see highlighted in yellow below. 
Please note: The DocumentsCorePack service has to be stopped first. 

Figure 14: Activate DCP service debugging